Systems and methods for facilitating login aid functionality in mobile commerce

ABSTRACT

This disclosure describes systems, methods, and computer-readable media related to systems and methods for facilitating login functionality in mobile commerce. A user device may receive information. The user device may transmit the information to a remote server. The user device may receive a token generated by the remote server based at least in part on the information. The user device may receive a request for the information. The user device may transmit the token associated with the information to the remote server. The user device may receive a notification that the remote server transmitted the requested information.

RELATED APPLICATIONS

This application claims priority to U.S. Ser. No. 61/699,728, titled“Systems and Methods for Implementing Mobile Commerce,” filed on Sep.11, 2012, and to U.S. Ser. No. 61/799,676, titled “Systems and Methodsfor Implementing Mobile Commerce,” filed on Mar. 15, 2013, the entirecontents of both are hereby incorporated by reference.

FIELD OF THE DISCLOSURE

The disclosure generally relates to mobile commerce, and moreparticularly, to systems and methods for facilitating login aidfunctionality in mobile commerce.

BACKGROUND

Commercial transactions to purchase certain goods and services are beingimplemented by consumers using mobile devices, such as smartphones.However, many commercial transactions are still cumbersome to implementsince many conventional point-of-sale (POS) terminals and devices,payment processing systems, and smartphone interfaces are not configuredfor user-friendly transactions.

BRIEF DESCRIPTION OF THE DISCLOSURE

The disclosure relates to systems and methods for implementing login aidfunctionality in mobile commerce.

In one embodiment, a method may be provided. A user device comprisingone or more processors may receive information. The user device maytransmit the information to a remote server. The user device may receivea token generated by the remote server based at least in part on theinformation. The user device may receive a request for the information.The user device may transmit the token associated with the informationto the remote server. The user device may receive a notification thatthe remote server transmitted the requested information.

In one aspect of an embodiment, the method may include transmitting, bythe user device, the token to a third party website for authenticationto the third party website.

In one aspect of an embodiment, the information may include at least oneof a phone number, a social network login, a username for a website,television application, or mobile application.

In one aspect of an embodiment, the method may include receiving, by theuser device, a notification that an association between the remoteserver and the user device has been removed responsive to receiving anindication via a website from a user of the user device.

In one aspect of an embodiment, transmitting the token associated withthe information to the remote server may further include receiving, bythe user device, a passcode; authenticating, by the user device, thepasscode; and in response to authenticating the passcode, transmitting,by the user device, the token associated with the information to theremote server.

In one aspect of an embodiment, receiving information may furtherinclude receiving information from one of a user or a third-partywebsite.

In one aspect of an embodiment, the method may include detecting, by theuser device, additional information to be added to a digital vault,wherein the additional information comprises at least one of a shippingaddress, a vehicle identification number, an account number, or a creditcard number.

In another embodiment, a computer-readable medium may storecomputer-executable instructions which, when executed by a processor,cause the processor to perform operations including receivinginformation; transmitting the information to a remote server; receivinga token generated by the remote server based at least in part on theinformation; receiving a request for the information; transmitting thetoken associated with the information to the remote server; receiving anotification that the remote server transmitted the requestedinformation.

In one aspect of an embodiment, the operations may include transmittingthe token to a third party website for authentication to the third partywebsite.

In one aspect of an embodiment, the information may include at least oneof a phone number, a social network login, a username for a website,television application, or mobile application.

In one aspect of an embodiment, the operations may include receiving anotification that an association between the remote server and the userdevice has been removed responsive to receiving an indication via awebsite from a user of the user device.

In one aspect of an embodiment, transmitting the token associated withthe information to the remote server may include receiving a passcode;authenticating the passcode; and in response to authenticating thepasscode, transmitting the token associated with the information to theremote server.

In one aspect of an embodiment, receiving information may furtherinclude receiving information from one of a user or a third-partywebsite.

In one aspect of an embodiment, the operations may further includedetecting additional information to be added to a digital vault, whereinthe additional information comprises at least one of a shipping address,a vehicle identification number, an account number, or a credit cardnumber.

In another embodiment, a system may include at least one memory storingcomputer-executable instructions; and at least one processor, whereinthe at least one processor may be configured to access the at least onememory and to execute the computer-executable instructions to receiveinformation; transmit the information to a remote server; receive atoken generated by the remote server based at least in part on theinformation; receive a request for the information; transmit the tokenassociated with the information to the remote server; and receive anotification that the remote server transmitted the requestedinformation.

In one aspect of an embodiment, the at least one processor may befurther configured to execute the computer-executable instructions totransmit the token to a third party website for authentication to thethird party website.

In one aspect of an embodiment, the information comprises at least oneof a phone number, a social network login, a username for a website,television application, or mobile application.

In one aspect of an embodiment, the at least one processor may befurther configured to execute the computer-executable instructions toreceive a notification that an association between the remote server andthe user device has been removed responsive to receiving an indicationvia a website from a user of the user device.

In one aspect of an embodiment, the at least one processor may befurther configured to execute the computer-executable instructions toreceive a passcode; authenticate the passcode; and in response toauthenticating the passcode, transmit the token associated with theinformation to the remote server.

In one aspect of an embodiment, the at least one processor may befurther configured to execute the computer-executable instructions toreceive information from one of a user or a third-party website.

In one aspect of an embodiment, the at least one processor may befurther configured to execute the computer-executable instructions todetect additional information to be added to a digital vault, whereinthe additional information comprises at least one of a shipping address,a vehicle identification number, an account number, or a credit cardnumber.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanyingdrawings. The use of the same reference numerals indicates similar oridentical components or elements; however, different reference numeralsmay be used as well to indicate components or elements which may besimilar or identical. Various embodiments of the disclosure may utilizeelements and/or components other than those illustrated in the drawings,and some elements and/or components may not be present in variousembodiments. Depending on the context, singular terminology used todescribe an element or a component may encompass a plural number of suchelements or components and vice versa.

FIG. 1 is a block diagram including various hardware and softwarecomponents a system for facilitating login aid functionality in mobilecommerce in accordance with one or more embodiments of the disclosure.

FIG. 2 is a block diagram that illustrates an example mobile commerceprogram application or module in accordance with one or more embodimentsof the disclosure.

FIG. 3 is a process flow diagram of an illustrative method forimplementing login aid functionality in mobile commerce in accordancewith one or more embodiments of the disclosure.

FIGS. 4A-4B are diagrams that depict example web pages for facilitatinglogin aid functionality in mobile commerce in accordance with one ormore embodiments of the disclosure.

FIG. 5 is a diagram that depicts example user interfaces for a mobiledevice for facilitating login aid functionality in mobile commerce inaccordance with one or more embodiments of the disclosure.

DETAILED DESCRIPTION

Certain embodiments of the disclosure will now be described more fullyhereinafter with accompanying drawings and corresponding description inFIGS. 1-5. This disclosure may, however, be embodied in many differentforms and should not be construed as limited to the embodiments setforth herein.

Overview

The disclosure relates to systems and methods for facilitating login aidfunctionality in mobile commerce. In one implementation, a mobilecommerce application program, also known as a mobile wallet or walletapp, can be downloaded or other otherwise implemented by a consumerand/or merchant via a mobile device or client device, such as asmartphone, cellphone, wearable computer, or tablet computer. The mobilecommerce application program can integrate both payment and loyaltyfunctionality for use by merchants and consumers to facilitate paymentand/or loyalty/reward transactions for goods and/or services, administerloyalty/reward programs, and receive loyalty/reward credit for a varietyof activities, including, for instance, visiting certain merchantsduring certain days and/or times as well as purchasing goods and/orservices. For example, according to certain embodiments of thedisclosure, a consumer can download a wallet app to his or hersmartphone or other mobile device, input and store payment deviceinformation in the wallet app, and then use the wallet app to pay amerchant for a movie ticket by transmitting an indication from thesmartphone or other mobile device to the merchant. Using the paymentdevice information, loyalty/reward credit can be generated by themerchant and credited to the consumer via a loyalty/reward programaccount for visiting the movie theater during an off-peak date/time aswell as purchasing the movie ticket. The wallet app can generate anoutput via the consumer's smartphone or mobile device to reflect theloyalty/reward credit to the consumer's associated loyalty/rewardprogram account as well as an electronic receipt for the consumer'smovie ticket purchase. In this manner, loyalty/reward programs canbecome easier to use for consumers since the mobile commerce applicationcan electronically track credits and various activities by the consumercan earn the consumer additional loyalty/reward credits. Further,different types of consumer loyalty can be rewarded, such as based onvisits, spending, performing any number of activities (e.g., sending afriend an email or text, joining a loyalty/reward program, tryingsomething new or different, etc.), or for ad-hoc reasons (e.g., latemerchant service).

In another implementation, one or more tools can be provided by a mobilecommerce application program to merchants and consumers to build closerties between them or otherwise connect them through increased and morefocused communications. For example, according to certain embodiments ofthe disclosure, a restaurant merchant can access, via a point of sale(POS) device or client device, a customized mobile commerce applicationor wallet app that has been downloaded to a consumer's mobile device orclient device. When the restaurant merchant wants to communicate withits customers about news, upcoming events, and new menu items, such asannouncing a special wine and cheese event for frequent customers. Therestaurant merchant can access one or more tools to send notificationsor messages to certain selected consumers via the wallet app onconsumer's mobile devices or client devices. The tools can facilitateaccess to demographic and consumer data (spending, visits, etc.); filterdata based on the demographic data, consumer data, and demographicand/or consumer groups; manage communication preferences (email, texts,notifications, etc.); and apply consumer preferences to selectedcommunications Consumers could be selected based on, for instance, thenumber of restaurant visits in the past 30 days. In this manner, themerchant can target certain groups of consumers with focused messagesand marketing campaigns, and thereby increase or otherwise improvemerchant-consumer contact.

In yet another implementation, a mobile commerce application program canprovide customized merchant applications to different merchants. Forexample, a local restaurant merchant may want to customize a wallet appor mobile commerce application program for downloading to or otherwiseaccessing via a consumer's mobile device or client device. The merchantcan access another mobile commerce application program and utilize oneor more tools to, for example, upload a merchant business logo, selectparameters for a loyalty/reward program, and select data fields forobtaining consumer information or asking consumer questions. In anyinstance, after the merchant has customized a wallet app, consumers canaccess or otherwise download the app to their respective mobile devicesor client devices, and initiate communications with the merchant via thecustomized wallet app. In certain other embodiments, a multi-merchantapp can be provided to consumers for download to or access by a mobiledevice or client device. In that instance, consumers can have theability to select from a list of merchants that communicate via themulti-merchant app. In certain other embodiments, a mobile commerceapplication program can provide services to any number of merchants whomay have their own respective apps, and the mobile commerce applicationprogram can provide a variety of payment, communication, advertising,and loyalty/reward services through, for example, one or moreapplication plug-ins that can interface between the merchant apps andthe mobile commerce application program. In this manner, a merchant cancustomize consumers' payment and/or loyalty/rewards experiences througha wallet app or mobile commerce application program.

In the above implementations and other embodiments described herein, amobile commerce application program, sometimes referred to as a walletapp, can be hosted or otherwise stored on a mobile device, clientdevice, server device, or any other processor-based device. Multipleinstances of mobile commerce application programs can operate within anetwork environment, such as described in FIG. 1, and each may havesimilar or different functionality, such as described in FIG. 2,according to various embodiments and implementations as describedherein.

CERTAIN EXAMPLE IMPLEMENTATIONS AND EMBODIMENTS

An example architecture or environment for a system 100 accordingvarious embodiments of the disclosure is shown in and described withrespect to FIG. 1. A mobile commerce application program or module, suchas 102, can be stored in memory 104 at a server device 106. In certainembodiments, a mobile commerce application program or module, such as108, can be stored in memory 110 at a merchant system computer 112 orassociated merchant device 114. In certain embodiments, a mobilecommerce application program or module, such as 116(1), can be stored inmemory 118(1) at a mobile device 120(1) associated with a consumer122(1) or user. In any instance, one or more mobile commerce applicationprograms or modules operating on respective computers, servers and/ormobile devices can implement some or all of the functionality describedherein.

As shown in FIG. 1, the system 100 may include or otherwise support oneor more merchant system computers 112 and/or associated merchant devices114, one or more consumer or mobile devices 120(1)-120(N), one or moreserver transaction processing systems 106, and one or more issuer orfinancial institution systems 124. A wide variety of different types ofconsumer or mobile devices 120(1)-120(N) may be provided or otherwisesupported, such as consumer computers and/or mobile communicationdevices. As desired, the system 100 may provide or otherwise support awide variety of other entities associated with payment transactions,such as one or more server transaction processing systems 106. Anynumber of suitable networks and/or communication channels, such as theillustrated networks 126, may facilitate communication between variouscomponents of the system 100.

With reference to FIG. 1, any number of merchant system computers 112and/or associated merchant devices 114 may be provided or otherwisesupported. In certain embodiments, these merchant system computers 112and/or associated merchant devices 114 may include one or morepoint-of-sale (POS) devices or terminals. As desired, each merchantsystem computer 112 and/or associated merchant device 114 may includeany number of processor-driven devices, including but not limited to, aserver computer, a mainframe computer, one or more networked computers,a desktop computer, a personal computer, a laptop computer, a mobilecomputer, a smartphone, a tablet computer, a wearable computer device,an application-specific circuit, or any other processor-based device.

A merchant system computer 112 and/or associated merchant device 114 maybe any suitable device that facilitates purchase transactions, such asthose in retail establishments, e-commerce and/or mobile transactions.In operation, the merchant system computer 112 and/or associatedmerchant device 114 may utilize one or more processors 128 to executecomputer-readable instructions that facilitate the hosting of one ormore mobile commerce application program services, the receipt ofpurchase transaction requests, and/or the processing of payment and/orloyalty/reward transactions. As a result of executing thesecomputer-readable instructions, a special purpose computer or particularmachine may be formed that facilitates the purchase and/orloyalty/reward transactions.

In addition to having one or more processors 128, the merchant systemcomputer 112 and/or associated merchant device 114 may further includeand/or be associated with one or more memory devices 110, input/output(“I/O”) interface(s) 130, network interface(s), and/or location services132. The memory 110 may be any computer-readable medium, coupled to theprocessor(s) 128, such as random access memory (“RAM”), read-only memory(“ROM”), and/or removable storage devices. The memory 110 may store awide variety of data files and/or various program modules, such as anoperating system (“OS”), one or more host modules, and/or one or moretransaction modules or transaction applications, such as mobile commerceapplication program 108. The data files may include any suitable datathat facilitates the operation of the merchant system computer 112and/or associated merchant device 114, and/or interaction of themerchant system computer 112 and/or associated merchant device 115 withone or more other components (e.g., one or more one or more consumer ormobile devices 120(1)-120(N), one or more server transaction processingsystems 106, one or more merchant acquiring platforms, one or moreissuer systems, one or more financial institution systems 124, etc.) ofthe system 100. For example, the data files may include informationassociated with one or more websites 134 (hosted by either a third partyand/or merchant), webpages, inventory information associated withavailable products, acquiring platform information, service providerinformation, information associated with the generation of paymentand/or loyalty/reward transactions and/or routing information forpayment and/or loyalty/reward transactions.

The OS may be suitable module that facilitates the general operation ofthe merchant system computer, as well as the execution of other programmodules. For example, the OS may be, but is not limited to, MicrosoftWindows®, Apple OSX™, Unix, a mainframe computer operating system (e.g.,IBM z/OS, MVS, OS/390, etc.), or a specially designed operating system.The host modules may include any number of suitable host modules thatmanage interactions and communications between the merchant systemcomputer 112 and/or associated merchant device 114, and externaldevices, such as the consumer or mobile devices 120(1)-120(N). Forexample, the host modules may include one or more Web server modulesthat facilitate the hosting of merchant websites and/or third partywebsites, such as 134, webpages, and/or transaction processing webpages.As another example, the host modules may include one or more cellularmodules and/or systems that facilitate cellular communication with oneor more mobile devices 120(1)-120(N).

The transaction modules or applications, such as the mobile commerceapplication program 108, may include any number of suitable softwaremodules and/or applications that facilitate the collection and/orprocessing of information association with a purchase transaction, suchas one or more identifiers of desired products (e.g., UPC identifiers)and/or services, a desired payment account, a desired type oftransaction (e.g., a card present transaction, a card not presenttransaction, etc.), consumer identification information, and/or anidentifier of a consumer or mobile device 120(1)-120(N) (e.g., a mobiledevice identifier, etc.). Based at least in part upon the collectedinformation, the transaction modules or applications may generate and/orcommunicate a wide variety of transaction-related requests, such aspayment processing and/or authorization requests and/or requests for oneor more value added services (“VAS”).

In one example embodiment, a transaction module, such as the mobilecommerce application program 108, may receive a request for a purchaseand/or loyalty/reward transaction (e.g., a request provided via a webpage, etc.). As desired, the transaction module may identify availablepayment options that are presented to a consumer (e.g., credit accountpayment options, debit account payment options, stored value accountpayment options, card present e-commerce payment options, etc.), and aconsumer selection of a payment option may be received. In the eventthat a card present transaction is requested, the transaction module mayobtain a mobile device identifier, for example, via an establishedcommunications session with a consumer's mobile device or in response torequesting the mobile device identifier from the consumer. Thetransaction module may then invoke or request that a server transactionprocessing system 106 invoke one or more suitable applications on themobile device, such as 120(1), (e.g., a wallet application, a mobilecommerce application program, a transaction module, etc.) in order toreceive validation information from the mobile device 120(1), such as anmPIN and/or a message (e.g., an encrypted message, etc.) derived from anmPIN and/or other information (e.g., a secure element identifier, anencryption key, etc.). The transaction module (or server transactionprocessing system) may then associate the validation information with aproposed transaction that is output for communication to an issuersystem or financial institution system 124 associated with a selectedpayment account. For example, the transaction module may append and/orincorporate the validation information into a transaction authorizationand/or settlement request. In this regard, the issuer system orfinancial institution system 124 may verify the validation informationand determine whether a card present e-commerce transaction will beallowed.

As desired, prior to the output of a proposed transaction, thetransaction module may invoke and/or request (e.g., request a servertransaction processing system, etc.) the invocation of a wide variety ofVAS associated with a transaction, such as the application of coupons,the award and/or redemption of loyalty rewards, etc. Additionally, inthe event that the transaction is authorized, the transaction module mayinvoke and/or request the invocation of a wide variety of VAS followingthe transaction, such as receipt delivery services, product registrationservices, etc. Indeed, a wide variety of suitable operations may beperformed by the transaction module. Similarly, in some embodiments, apayment device, such as 135(1)-135(N), for example a payment card,credit card, debit card, stored value card, smart card, etc., may beassociated with a respective consumer, such as 122(1)-122(N). Thepayment device, such as 135(1), can be used to request a purchase and/orloyalty/reward transaction when presented to a merchant system computer112 and/or merchant computer device 114, either directly by the consumer135(1) or via a consumer's mobile device, such as 120(1)-120(N). Inthese instances, an associated transaction module, such as the mobilecommerce application program 108 associated with the merchant computersystem 112 and/or merchant computer device 114, can receive paymentdevice information, such as an account number and/or other paymentdevice information, and communicate, via one or more networks 126, someor all of the payment device information to an issuer system orfinancial institution system 124 with the proposed transactioninformation for processing.

Example application programs or modules associated with the operationsthat may be performed by a transaction module or mobile commerceapplication program 108 and/or the merchant system computer 112 and/orassociated merchant device 114 are described in greater detail belowwith reference to FIG. 2.

With continued reference to the merchant system computer 112 and/orassociated merchant device 114, the one or more I/O interfaces 130 mayfacilitate communication between the merchant system computer 112 and/orassociated merchant device 114 and one or more input/output devices; forexample, one or more user interface devices, such as a display, akeypad, a mouse, a pointing device, a gesture detection device, an eyemovement detection device, a control panel, a touch screen display, aremote control, a microphone, a speaker, a consumer device reader, etc.,that facilitate user interaction with the merchant system computer 112and/or associated merchant device 114. The one or more networkinterfaces may facilitate connection of the merchant system computer 112and/or associated merchant device 114 to one or more suitable networks,such as 126, and/or communication links. In this regard, the merchantsystem computer 112 and/or associated merchant device 114 may receiveand/or communicate information to other components of the system 100,such as the consumer or mobile devices, for example 120(1)-120(N), theserver transaction processing systems 106, and/or the issuer orfinancial institution systems 124.

In certain embodiments, a merchant computer system 112 and/or associatedmerchant computer device 114 can be associated with a merchant location136, such as a retail store or “bricks and mortar”-type establishment.The merchant location 136 may include a code 138, such as a QR code, barcode, or other machine readable code, wherein consumers can utilize arespective consumer or mobile device to scan or read the code to obtaininformation associated with a merchant, such as a merchantloyalty/rewards program.

In certain embodiments, a bill 139 can be generated by a merchantcomputer system 112 and/or merchant system device 114 and transmitted toa consumer's mobile device, such as 120(1). The bill can include billinformation, such as a merchant name, merchant account number or code,list of goods sold, list of services rendered, an itemized amount for agood and/or service, service charge or tip, a suggested service chargeor tip, and a total amount.

Additionally, with continued reference to FIG. 1, any number of consumeror mobile devices 120(1)-120(N) may be provided or otherwise supported.Examples of suitable consumer or mobile devices can include, but are notlimited to, personal computers and/or mobile communication devices(e.g., mobile phones, smart phones, wearable devices, etc.), etc.According to an aspect of the disclosure, a consumer or mobile device,such as 120(1) may be a suitable device that is capable of interactionwith other components of the system 100 during the request and/orcompletion of an e-commerce transaction. For example, a personalcomputer or mobile device may be utilized to access one or moree-commerce websites, such as 134, including those hosted by the merchantsystem computer, such as 112, identify products and/or services to bepurchased, request a purchase and/or loyalty/reward transaction, and/orinteract with the merchant system computer 112, merchant system device114, and/or other components of the system 100 (e.g., the servertransaction processing system 106, etc.) during the completion of apayment and/or loyalty/reward transaction. In one example embodiment, amobile device, such as 120(1), may be utilized to request a paymentand/or loyalty/reward transaction and/or to provide validationinformation during the processing of the payment and/or loyalty/rewardtransaction. In another example embodiment, a personal computer may beutilized to request a payment and/or loyalty/reward transaction, andcommunication may be established with a mobile device, such as 120(1),in order to facilitate provision of validation information.

As desired, a consumer or mobile device, such as 120(1), may be anynumber of processor-driven devices, including but not limited to, apersonal computer, a mobile computer, an application-specific circuit, aminicomputer, a microcontroller, and/or any other processor-baseddevice. The components of an example mobile device, such as 120(1), willnow be described in greater detail, and it will be appreciated that apersonal computer may include similar components. With reference to themobile device 120(1), the mobile device 120(1) may utilize one or moreprocessors 140(1) to execute computer-readable instructions thatfacilitate the general operation of the mobile device 120(1) (e.g., callfunctionality, etc.) and/or communication with a merchant systemcomputer 112, merchant system device 114, and/or other components of thesystem 100 (e.g., the server transaction processing system 106) forpayment and/or loyalty/reward transaction purposes. As a result ofexecuting these computer-readable instructions, a special purposecomputer or particular machine may be formed that facilitates thecompletion of payment and/or loyalty/reward transactions.

In addition to having one or more processors, the mobile device, such as120(1)-120(N), may further include and/or be associated with one or morememory devices 118(1)-118(N), input/output (“I/O”) interface(s)142(1)-142(N), network interface(s), and/or location services144(1)-144(N). The memory 118(1)-118(N) may be any computer-readablemedium, coupled to the processor(s) 140(1)-140(N), such as random accessmemory (“RAM”), read-only memory (“ROM”), and/or removable storagedevices. The memory 118(1)-118(N) may store a wide variety of data filesand/or various program modules, such as an operating system (“OS”)and/or one or more transaction modules or applications, such as a mobilecommerce application program 116(1)-116(N). In certain embodiments, amobile device, such as 120(1), may include one or more secure elementsconfigured to securely store and/or access information, such as paymentapplications, payment account information, validation information (e.g.,a stored mPIN, etc.), encryption information, and/or othertransaction-related information. The secure elements may be stored inthe memory 118(1) and/or included as a separate component of the mobiledevice 120(1). For example, a secure element may be a separate chip thatis configured to communicate with primary computing functionality forthe mobile device. As desired, one or more of the transaction modules,such as the mobile commerce application program 116(1), may be stored ona secure element. The transaction modules may be invoked by othercomponents of the mobile device 120(1) and/or by one or more othercomponents of the system 100, such as the merchant system computer 112,merchant system device 114, and/or the server transaction processingsystem 106.

The data files may include any suitable data that facilitates theoperation of the mobile device, such as 120(1), and/or interaction ofthe mobile device 120(1) with one or more other components (e.g., amerchant system computer 112, merchant system device 114, a servertransaction processing system 106, etc.) of the system 100. For example,the data files may include information associated with accessing thesecure elements, information associated with invoking transactionmodules, and/or information associated with accessing and/or processingvalidation data (e.g., an mPIN, etc.). The OS may be a suitable modulethat facilitates the general operation of the mobile device, such as120(1), as well as the execution of other program modules. For example,the OS may be, but is not limited to, a suitable mobile OS or aspecially designed operating system. As desired, the mobile device120(1) may also include one or more suitable browser applications thatfacilitate the access of one or more webpages hosted by the merchantsystem computer 112, and/or third party or merchant websites, such as134.

The transaction modules may include one or more suitable softwaremodules and/or applications configured to facilitate purchasetransactions, such as payment and/or loyalty/reward transactions, onbehalf of the mobile device, such as 120(1). In certain embodiments, atransaction module or mobile commerce application program, such as116(1), may also facilitate communication with a server transactionprocessing system, such as 106, or a trusted service manager. A widevariety of suitable techniques may be utilized to install a transactionmodule on the mobile device, such as 120(1). For example, a transactionmodule may be provisioned to the mobile device 120(1) by a servertransaction processing system 106 and/or by an issuer or financialinstitution system 124. Additionally, during the installation and/orregistration of the transaction module, a wide variety of validationinformation may be generated and/or identified. For example, a consumer,such as 122(1) may be prompted to enter an mPIN, such as amulti-character and/or multi-numeral code, to an associated mobiledevice, such as 120(1). As desired, the mPIN may be stored on a secureelement. Additionally, the PIN and/or a wide variety of informationderived from the mPIN (e.g., an encrypted mPIN, etc.) may be provided toone or more issuer or financial institution systems, such as 124, or anissuer system associated with an issuer of a payment account (e.g., acredit account, a debit account, a stored value account, etc.) that isassociated with the transaction module.

According to an aspect of the disclosure, following registration and/oractivation of the transaction module, the transaction module may beinvoked during a payment and/or loyalty/reward transaction. For example,the transaction module may be invoked by a merchant system computer 112,merchant system device 114, or by a server transaction processing system106 at the request of the merchant system computer 112 and/or merchantsystem device 114. In certain embodiments, the transaction module may beinvoked following a consumer request to conduct a payment and/orloyalty/reward transaction and the identification of the mobile device,such as 120(1), by the merchant system computer 112, merchant systemdevice 114, or server transaction processing system 106. Following theinvocation of the transaction module, a request for validation dataand/or payment and/or loyalty/reward account data may be received. Asdesired, the transaction module may prompt the consumer for entry of anmPIN, and an mPIN value entered by the consumer, such as 122(1), (e.g.,by a keypad, touchscreen, etc.) may be identified. A stored mPIN valuemay then be accessed from the secure element and compared to the enteredmPIN value. In this regard, the entered mPIN value may be authenticated.If the entered mPIN value is not authenticated, then the transactionmodule may reject a proposed transaction and direct the output of asuitable error message.

If, however, the entered mPIN value is authenticated, then thetransaction module may provide payment account data and associatedvalidation data to the merchant system computer 112, merchant systemdevice 114, or server transaction processing system 106. A wide varietyof different types of validation data may be provided as desired invarious embodiments, including but not limited to, an mPIN entered bythe consumer 122(1), an indication that the entered mPIN wasauthenticated by the mobile device 120(1) and/or the secure element, anencrypted version of the entered mPIN, and/or an encrypted version ofthe stored mPIN. In one example embodiment, an entered mPIN may beauthenticated, encrypted, and provided to the merchant system computer(or a server transaction processing system). In this regard, theencrypted mPIN may be provided to the issuer or financial institutionsystem, such as 124, for authentication and/or risk analysis purposes.

Examples of the operations of the transaction module and/or the mobiledevice are described in greater detail below with reference to the otherfigures.

The one or more I/O interfaces, such as 142(1)-142(N), may facilitatecommunication between the mobile device, such as 120(1) and one or moreinput/output devices; for example, one or more user interface devices,such as a display, a keypad, a touch screen display, a microphone, aspeaker, etc., that facilitate user interaction with the mobile device120(1). Further, the one or more network interfaces may facilitateconnection of the mobile device, such as 120(1), to one or more suitablenetworks, for example, the network(s) 126 illustrated in FIG. 1. In thisregard, the mobile device, such as 120(1), may receive and/orcommunicate information to other components of the system 100.

With continued reference to FIG. 1, as desired in various embodiments,any number of server transaction processing systems, such as 106, may beprovided or otherwise supported. A server transaction processing system106 may facilitate the backend processing of a purchase transaction,such as a payment and/or loyalty/reward transaction. In certainembodiments, an issuer system may include similar components as thosediscussed above for the merchant system computer 112 and/or merchantsystem device 114. For example, server transaction processing system 106may include any number of processors 146, memories, I/O interfaces 148,and/or network interfaces. In certain embodiments, a server transactionprocessing system 106 can include one or more transaction modules, suchas a mobile commerce application program 102 and/or a social networkintegration program application 150. In any instance, the transactionmodules can facilitate communications and/or interactions with anynumber of consumer or mobile devices such as 120(1)-120(N), merchantcomputer systems such as 112, merchant computer devices 114, data stores151, third party websites such as 134, and financial institution systemssuch as 124. In certain embodiments, a service transaction processingsystem, such as 106, can host a social network integration programapplication, such as 150, configured to communicate via any number ofsocial network services and/or websites to obtain information from theservices and/or websites, for example, product and/or service data 152on a third party or merchant website, such as 134.

Furthermore, as desired, a server transaction processing system, such as106, may provide a wide variety of transaction module provisioningservices. Additionally, a server transaction processing system, such as106, may provide a wide variety of transaction-related and/or valueadded services (“VAS”) in association with transactions, such as couponredemption services, loyalty/reward services, location-based services,electronic receipt services, product registration services, warrantyservices, coupon issuance services, and/or the routing of a proposedtransaction to an issuer for approval and/or settlement purposes. Incertain embodiments, a server transaction processing system, such as106, may include similar components as those discussed above for themerchant system computer, such as 112, and/or merchant system device,such as 114. For example, a server transaction processing system, suchas 106, may include any number of processors, memories, I/O interfaces,and/or network interfaces.

With continued reference to FIG. 1, as desired in various embodiments,any number of issuer or financial institution systems, such as 124, maybe provided or otherwise supported. An issuer or financial institutionsystem, such as 124, may facilitate the backend processing of a paymentand/or loyalty/reward transaction, such as a payment for an e-commercetransaction. For example, an issuer or financial institution system,such as 124, may host a payment processing application program, such as154, or module to facilitate the approval, authentication, and/orsettlement of a payment transaction. In certain embodiments, a paymenttransaction may be routed to an issuer or financial institution system,such as 124, via a suitable transaction network (e.g., a debit network,a credit network, etc.), and the issuer or financial institution system,such as 124, may evaluate the payment transaction via the paymentprocessing application program, such as 154, or module. An approval orrejection of the payment transaction may then be output forcommunication to a merchant system computer, such as 112, and/ormerchant system device 114. The issuer or financial institution system,such as 124, may then facilitate the settlement of the paymenttransaction. In certain embodiments, an issuer or financial institutionsystem, such as 124, may include similar components as those discussedabove for the merchant system computer 112 and/or merchant system device114. For example, an issuer or financial institution system, such as124, may include any number of processors 156, memories 158, I/Ointerfaces 160, and/or network interfaces.

In certain embodiments of the disclosure, an issuer or financialinstitution system, such as 124, may receive validation information inassociation with a purchase and/or loyalty/reward transaction.

A wide variety of suitable networks, individually and/or collectivelyshown as 126 in FIG. 1, may be utilized in association with embodimentsof the disclosure. Certain networks may facilitate use of a wide varietyof e-commerce-related communication. For example, one or moretelecommunication networks, cellular networks, wide area networks (e.g.,the Internet), and/or other networks may be provided or otherwisesupported. Other networks may facilitate communication oftransaction-related communications. For example, one or more transactionnetworks, such as branded networks (e.g., a VISA network, etc.), debitand/or PIN networks, and/or a wide variety of other suitable transactionnetworks may facilitate communication of transaction-relatedcommunications, such as e-commerce transactions. Due to networkconnectivity, various methodologies as described herein may be practicedin the context of distributed computing environments. It will also beappreciated that the various networks may include a plurality ofnetworks, each with devices such as gateways and routers for providingconnectivity between or among networks. Additionally, instead of, or inaddition to, a network, dedicated communication links may be used toconnect various devices in accordance with an example embodiment.

The system 100 shown in and described with respect to FIG. 1 is providedby way of example only. Numerous other operating environments, systemarchitectures, and device configurations are possible. Other systemembodiments can include fewer or greater numbers of components and mayincorporate some or all of the functionality described with respect tothe system components shown in FIG. 1. Accordingly, embodiments of thedisclosure should not be construed as being limited to any particularoperating environment, system architecture, or device configuration.

FIG. 2 shows an example mobile commerce application program 200, similarto the mobile commerce application programs 102, 108, and 116(1)-116(N)in FIG. 1 that can operate with respect to the system 100 shown inFIG. 1. The mobile commerce application program 200 shown in FIG. 2 caninclude, for example, a loyalty/rewards module 202, a check-in-to-paymodule 204, an interruptive alert module 206, a share redeemed offermodule 208, a notification or messaging module 210, a restaurant mobilepayment module 212, a check-in-to-pay at QSR module 214, a split thebill module 216, a lifecycle shopping module 218, a linking transactionmodule 220, a mobile device login module 222, a bill payment module 224,a multi-consumer remote payment module 226, an instant issuance module228, a check-in to pump gas module 230, a buy car wash module 232, adrive consumer inside module 234, a tokenization module 236, and a codegeneration module 238. Some or all of the modules 202-238 are describedherein with respect to certain mobile commerce functionality, associatedprocesses, and features. FIG. 3 illustrates certain processes associatedwith some or all of the modules comprising the example mobile commerceapplication program 200 in FIG. 2.

While the various modules 202-238 are shown by way of example, fewer orgreater numbers of modules can be present in various embodiments of amobile commerce application program. Furthermore, various functionalitydescribed with respect to one module may be performed by multiplemodules in other embodiments of the disclosure.

Mobile Device Login Aid

In some instances, consumers desire to access a third party websiteusing login information, such as a username and passcode. Certainembodiments of the disclosure can provide systems and processes forusing a mobile device login aid, such as providing functionality topermit a mobile phone to act as a login aid. A consumer may sign up fora login aid system and service and enter his or her username andpasscode combinations for any number of websites he or she uses. In oneembodiment, a tool or feature can automatically collect logininformation as the consumer logs in to the websites. In any instance,when the consumer re-visits a website, the consumer can be prompted toenter his or her mobile phone number and a passcode. After the login aidsystem and service authenticates the consumer, a message can betransmitted to the consumer's mobile phone to “Accept” or “Reject”logging into the website. If the consumer approves, the logincredentials or a token of the credentials can be sent to the website andthe can be logged into the website without having to manually enter theusername and passcode combination. In this manner, the consumer needsonly to remember his mobile phone number (or other credential such as asocial network login or email address) and a passcode to access multiplerevisited websites.

In one embodiment, by way of a mobile device 120(1) or other clientdevice, such as a laptop computer or tablet, a consumer can initiate amobile device login aid module 222 in a payment application program orapp accessible via the consumer's mobile device 120(1) or other clientdevice. For example, in a payment application or app accessible via theconsumer's mobile device 120(1) or other client device, a set ofcomputer-executable instructions can be configured to receive anindication from the consumer of a visited website username and passcodeto be stored, and can be further configured to store the visited websiteusername and passcode. In certain embodiments, the set ofcomputer-executable instructions can be configured to prompt theconsumer whether to store a previously entered username and passcode fora visited website. In certain embodiments, the set ofcomputer-executable instructions can be configured to, after receivingconsumer approval, automatically store previously entered usernames andpasscodes for visited websites. In any instance, the set ofcomputer-executable instructions can be configured to receive anindication that a previously visited website is currently being visitedby the consumer, and the instructions can be further configured toprompt the consumer to enter mobile phone number and passcode associatedwith the mobile phone number. Upon receipt of the consumer's mobilephone number and passcode, the set of computer-executable instructionscan be configured to authenticate the consumer's identity, and uponauthentication, the instructions can be further configured to providethe consumer's previously stored username and passcode for the currentlyvisited website.

Using some or all of the above systems and processes, functionality forproviding a mobile device login aid can be enabled. In this manner,consumers can better manage multiple usernames and passcodes for variousvisited websites, and can access all previously stored usernames andpasscodes for various visited websites with a single mobile devicenumber and associated passcode, which can enhance the consumer onlinepurchase and viewing experience.

FIG. 3 is a flow diagram of a method 300 for a mobile device login aidin accordance with an embodiment of the disclosure. Various operationsof the methods described below can be performed by the system componentsdescribed above and shown in FIGS. 1 and 2. In brief overview, at block302, a mobile device login module 222 of a mobile device 120(1) mayreceive information. At block 304, the mobile device login module 222 ofthe mobile device 120(1) may transmit the information to a remoteserver. At block 306, the mobile device login module 222 of the mobiledevice 120(1) may receive a token generated by the remote service basedat least in part on the information. At block 308, the mobile devicelogin module 222 of the mobile device 120(1) may receive a request forthe information. At block 310, the mobile device login module 222 of themobile device 120(1) may transmit the token associated with theinformation to the remote server. At block 312, the mobile device loginmodule 222 of the mobile device 120(1) may receive a notification thatthe remote server transmitted the requested information.

At block 302, the mobile device login module 222 of the mobile device120(1) may receive information. In some embodiments, the information maybe received from a user. In some embodiments, the information may bereceived from a third-party website. In some embodiments, theinformation may be received from an application executing on the mobiledevice 120(1). The information may be usernames and passwords for thirdparty websites. In some embodiments, the information may be informationthat may be difficult to type on a mobile device 120(1), such asshipping addresses, account numbers, VIN numbers, identificationnumbers, such as a driver's license number, credit card numbers andtheir associated information, such as expiration dates and securitycodes, or the like.

In some embodiments, the system may be configured to enable automaticaddition of usernames and passwords for visited websites. In someembodiments, the user may need to explicitly type in the username andpassword into the mobile device 120(1). In some embodiments, the mobiledevice 120(1) may detect a username and password used on third-partysites. In some embodiments, the system may detect information that maybe added to the digital vault. For example, the mobile device 120(1) maydetect information that may detect shipping addresses, VINs, accountnumbers, credit cards numbers, and the like.

At block 304, the mobile device login module 222 of the mobile device120(1) may transmit the information to a remote server. The user maytransmit the receive information to the remote server to be tokenizedand/or encrypted. In some embodiments, the remote server may store theinformation in association with the token so that when contacted by athird party website, the remote server may transmit the requestedinformation.

At block 306, the mobile device login module 222 of the mobile device120(1) may receive a token generated by the remote service based atleast in part on the information. In some embodiments, the mobile device120(1) may transmit the token to the requesting third party website. Thethird party website may use the token to authenticate the user andpermit the user to login without having to manually enter a username andpassword.

At block 308, the mobile device login module 222 of the mobile device120(1) may receive a request for the information. In some embodiments,the mobile device login module 222 of the mobile device 120(1) mayreceive a request for information from a third party website. The thirdparty website may transmit the request in response to the user enteringa credential and possible passcode on the third party website. In someembodiments, the mobile device login module 222 of the mobile device120(1) may receive a request from a mobile application executing on themobile device 120(1), a television application, or the like.

At block 310, the mobile device login module 222 of the mobile device120(1) may transmit the token associated with the information to theremote server. At block 312, the mobile device login module 222 of themobile device 120(1) may receive a notification that the remote servertransmitted the requested information.

In some embodiments, a user may type in an identifier, such as a phonenumber, a social network login, or a username for a website, televisionapplication, and/or mobile application. In some embodiments, a passcodemay also be entered. The website or application may transmit anotification to the mobile device 120(1). The mobile device login module222 of the mobile device 120(1) may transmit the tokenized informationto the website or application for authentication. The website orapplication may communicate with the remote server to obtain theinformation associated with the tokenized information or may use ade-tokenization service to de-tokenize the information.

In some embodiments, the system may provide security features inassociation with the mobile device login aid. For example, if a userloses their phone, the system may terminate the mobile application fromthe remote server. In some embodiments, a user may need to login to awebsite to notify the system that the phone was lost. The system mayterminate or break the association of the system with the phone so thatthe application on the phone would no longer be able to work communicatewith the remote server to work properly.

In some embodiments, the third party websites may require the user toenter their credentials as well as a passcode to increase security. Insome embodiments, if the passcode is incorrect, the system would notenable the phone to communicate with the website to transmit therequested information or the tokenized information.

In some embodiments, the mobile device login module 222 of the mobiledevice 120(1) may require the user to enter a passcode in order toauthorize the transmission of the requested information to the thirdparty website.

In some embodiments, if the information, such as a username and passwordor shipping address has not been used for a pre-determined period, thesystem may delete the information. In some embodiments, the system mayask for confirmation from the user prior to deleting the information.

In some embodiments, the mobile device login module 222 of the mobiledevice 120(1) may be configured to generate a secure password for athird party website and store the password for future use.

Using some or all of the above systems and processes, a technicalsolution implementing bill payment functionality in mobile commerce canbe enabled. For example, technical solutions involving approving and/orrejecting a bill payment using a mobile device can be implemented. Inthis manner, technical solutions can be implemented such that consumerscan better manage budgets as well as consumer spending, and be betterinformed about information that may affect the consumer's decision tocomplete a purchase transaction.

FIGS. 4A-4B are diagrams that depict example web pages for facilitatinglogin aid functionality in mobile commerce in accordance with one ormore embodiments of the disclosure. In FIG. 4A, a web page 400 that maybe accessed by a laptop or other user device where a user may enter amobile number and a passcode associated with the login aid. FIG. 4B is awebpage 450 that may be displayed in response to entering the requestedinformation in 400. Webpage 450 indicates that a notification has beensent to a mobile device 120(1) to validate login credentials toauthorize the login on the mobile device 120(1).

FIG. 5 is a diagram that depicts example user interfaces for a mobiledevice 120(1) for facilitating login aid functionality in mobilecommerce in accordance with one or more embodiments of the disclosure.User interface 500 depicts the mobile device 120(1) receiving anotification from a third party web page. The user has the option toeither accept or reject the request. If the user chooses to accept therequest, then user interface 550 may be rendered, which allows the userto confirm sending login credentials to the third party interface.

CONCLUSION

The operations and processes described and shown above may be carriedout or performed in any suitable order as desired in variousimplementations. Additionally, in certain implementations, at least aportion of the operations may be carried out in parallel. Furthermore,in certain implementations, less than or more than the operationsdescribed may be performed.

Certain aspects of the disclosure are described above with reference toblock and flow diagrams of systems, methods, apparatuses, and/orcomputer program products according to various implementations. It willbe understood that one or more blocks of the block diagrams and flowdiagrams, and combinations of blocks in the block diagrams and the flowdiagrams, respectively, can be implemented by computer-executableprogram instructions Likewise, some blocks of the block diagrams andflow diagrams may not necessarily need to be performed in the orderpresented, or may not necessarily need to be performed at all, accordingto some implementations.

These computer-executable program instructions may be loaded onto aspecial-purpose computer or other particular machine, a processor, orother programmable data processing apparatus to produce a particularmachine, such that the instructions that execute on the computer,processor, or other programmable data processing apparatus create meansfor implementing one or more functions specified in the flow diagramblock or blocks. These computer program instructions may also be storedin a computer-readable storage media or memory that can direct acomputer or other programmable data processing apparatus to function ina particular manner, such that the instructions stored in thecomputer-readable storage media produce an article of manufactureincluding instruction means that implement one or more functionsspecified in the flow diagram block or blocks. As an example, certainimplementations may provide for a computer program product, comprising acomputer-readable storage medium having a computer-readable program codeor program instructions implemented therein, said computer-readableprogram code adapted to be executed to implement one or more functionsspecified in the flow diagram block or blocks. The computer programinstructions may also be loaded onto a computer or other programmabledata processing apparatus to cause a series of operational elements orsteps to be performed on the computer or other programmable apparatus toproduce a computer-implemented process such that the instructions thatexecute on the computer or other programmable apparatus provide elementsor steps for implementing the functions specified in the flow diagramblock or blocks.

Accordingly, blocks of the block diagrams and flow diagrams supportcombinations of means for performing the specified functions,combinations of elements or steps for performing the specified functionsand program instruction means for performing the specified functions. Itwill also be understood that each block of the block diagrams and flowdiagrams, and combinations of blocks in the block diagrams and flowdiagrams, can be implemented by special-purpose, hardware-based computersystems that perform the specified functions, elements or steps, orcombinations of special-purpose hardware and computer instructions.

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainimplementations could include, while other implementations do notinclude, certain features, elements, and/or operations. Thus, suchconditional language is not generally intended to imply that features,elements, and/or operations are in any way required for one or moreimplementations or that one or more implementations necessarily includelogic for deciding, with or without user input or prompting, whetherthese features, elements, and/or operations are included or are to beperformed in any particular implementation.

Many modifications and other implementations of the disclosure set forthherein will be apparent having the benefit of the teachings presented inthe foregoing descriptions and the associated drawings. Therefore, it isto be understood that the disclosure is not to be limited to thespecific implementations disclosed and that modifications and otherimplementations are intended to be included within the scope of theappended claims. Although specific terms are employed herein, they areused in a generic and descriptive sense only and not for purposes oflimitation.

What is claimed is:
 1. A computer-implemented method comprising:receiving, by a user device comprising one or more processors,information; transmitting, by the user device, the information to aremote server; receiving, by the user device, a token generated by theremote server based at least in part on the information; receiving, bythe user device, a request for the information; transmitting, by theuser device, the token associated with the information to the remoteserver; receiving, by the user device, a notification that the remoteserver transmitted the requested information.
 2. Thecomputer-implemented method of claim 1, further comprising:transmitting, by the user device, the token to a third party website forauthentication to the third party website.
 3. The computer-implementedmethod of claim 1, wherein the information comprises at least one of aphone number, a social network login, a username for a website,television application, or mobile application.
 4. Thecomputer-implemented method of claim 1, further comprising: receiving,by the user device, a notification that an association between theremote server and the user device has been removed responsive toreceiving an indication via a website from a user of the user device. 5.The computer-implemented method of claim 1, wherein transmitting thetoken associated with the information to the remote server furthercomprising: receiving, by the user device, a passcode; authenticating,by the user device, the passcode; and in response to authenticating thepasscode, transmitting, by the user device, the token associated withthe information to the remote server.
 6. The computer-implemented methodof claim 1, wherein receiving information further comprises: receivinginformation from one of a user or a third-party website.
 7. Thecomputer-implemented method of claim 1, further comprising: detecting,by the user device, additional information to be added to a digitalvault, wherein the additional information comprises at least one of ashipping address, a vehicle identification number, an account number, ora credit card number.
 8. A computer-readable medium storingcomputer-executable instructions which, when executed by a processor,cause the processor to perform operations comprising: receivinginformation; transmitting the information to a remote server; receivinga token generated by the remote server based at least in part on theinformation; receiving a request for the information; transmitting thetoken associated with the information to the remote server; receiving anotification that the remote server transmitted the requestedinformation.
 9. The computer-readable medium of claim 8, the operationsfurther comprising: transmitting the token to a third party website forauthentication to the third party website.
 10. The computer-readablemedium of claim 8, wherein the information comprises at least one of aphone number, a social network login, a username for a website,television application, or mobile application.
 11. The computer-readablemedium of claim 8, the operations further comprising: receiving anotification that an association between the remote server and the userdevice has been removed responsive to receiving an indication via awebsite from a user of the user device.
 12. The computer-readable mediumof claim 8, wherein transmitting the token associated with theinformation to the remote server further comprising: receiving apasscode; authenticating the passcode; and in response to authenticatingthe passcode, transmitting the token associated with the information tothe remote server.
 13. The computer-readable medium of claim 8, whereinreceiving information further comprises: receiving information from oneof a user or a third-party website.
 14. The computer-readable medium ofclaim 8, the operations further comprising: detecting additionalinformation to be added to a digital vault, wherein the additionalinformation comprises at least one of a shipping address, a vehicleidentification number, an account number, or a credit card number.
 15. Asystem comprising: at least one memory storing computer-executableinstructions; and at least one processor, wherein the at least oneprocessor is configured to access the at least one memory and to executethe computer-executable instructions to: receive information; transmitthe information to a remote server; receive a token generated by theremote server based at least in part on the information; receive arequest for the information; transmit the token associated with theinformation to the remote server; receive a notification that the remoteserver transmitted the requested information.
 16. The system of claim15, wherein the at least one processor is further configured to executethe computer-executable instructions to: transmit the token to a thirdparty website for authentication to the third party website.
 17. Thesystem of claim 15, wherein the information comprises at least one of aphone number, a social network login, a username for a website,television application, or mobile application.
 18. The system of claim15, wherein the at least one processor is further configured to executethe computer-executable instructions to: receive a notification that anassociation between the remote server and the user device has beenremoved responsive to receiving an indication via a website from a userof the user device.
 19. The system of claim 15, wherein to transmit thetoken associated with the information to the remote server, the at leastone processor is further configured to execute the computer-executableinstructions to: receive a passcode; authenticate the passcode; and inresponse to authenticating the passcode, transmit the token associatedwith the information to the remote server.
 20. The system of claim 15,wherein to receive information, the at least one processor is furtherconfigured to execute the computer-executable instructions to: receiveinformation from one of a user or a third-party website.
 21. The systemof claim 15, wherein the at least one processor is further configured toexecute the computer-executable instructions to: detect additionalinformation to be added to a digital vault, wherein the additionalinformation comprises at least one of a shipping address, a vehicleidentification number, an account number, or a credit card number.